@blueorangutan package

@davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: ✔️centos ✔️debian ✔️archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/444 (JID-2100)

@rhtyd good to go!

@rhtyd good to go!

@rhtyd Right now, listLdapUsers does not support search or pagination

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: ✔️centos ✔️debian ✔️archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/444 (JID-2108)

@davidjumani add information pop-over like other forms, add doc-link to the custom form (somewhere put a <a-icon for question and link to this.$config.docBase + ....)
Also test/check against old UI.

Primate API call runs:

domainid: 78ec0573-03fb-4c02-872a-b0f3a86471dc
roleid: 16919363-5fe0-11ea-9a56-1e006800018c
timezone: ACT
networkdomain: net-domain
group: group
username: ldapman
command: importLdapUsers
response: json

Legacy UI runs:

command: importLdapUsers
domainid: e4874e10-5fdf-11ea-9a56-1e006800018c
account: acount-name
roleid: 16919363-5fe0-11ea-9a56-1e006800018c
timezone: Pacific/Johnston
networkdomain: net-domain
group: ldap-group
response: json

Mismatch account not passed, instead username? Also, the label 'Group' should say 'LDAP Group'. Check the form against old UI.

@rhtyd In the legacy UI, although the default filter is 'No Filter', the initial listLdapUsrers call uses 'Any Domain' as its filter. In this case, using 'No Filter' for the initial listLdapUsrers call. Should I change it to match the legacy UI ?

@davidjumani can you discuss with @DaanHoogland ?

Discussed with @DaanHoogland Good to go!

looks good